Use Intent as the canonical system name - #10

What changed

• makes Intent the only name for the layer, corpus, artifacts, nodes, checker contracts, and operational procedures
• migrates requirement IDs, diagnostic rules, schema versions, CLI messages, Rust public types, document grammar, fixtures, tests, CI assertions, and tracked path names as one atomic change
• renames the interview procedure and integration test paths to their Intent forms
• records the owner-approved naming decision and bumps the crate to 0.2.0
• adds a CI guard that rejects the retired name in tracked content or filenames
• retires the captured provider report instead of rewriting historical raw output with identifiers it never emitted
• ignores local tmp/ render and scratch artifacts

Why

The repository and checker already used Intent, while the corpus and machine contracts retained a second concrete system name. That split left 1,298 references across prose, paths, schemas, code, tests, and CI and made it unclear whether Intent named only the repository or the layer itself.

This change establishes one canonical vocabulary and removes the translation rule across human- and machine-readable surfaces.

Impact

This is intentionally breaking. Downstream consumers must update structured IDs, diagnostic rule matching, schema-version checks, command names, public Rust type names, and required Intent document headings. Compatibility aliases are intentionally not retained because they would preserve the two-name model.

Validation

• cargo fmt --check --manifest-path crates/intent/Cargo.toml
• cargo clippy --locked --manifest-path crates/intent/Cargo.toml --all-targets -- -D warnings
• cargo test --locked --manifest-path crates/intent/Cargo.toml — 18 tests passed
• release build with --locked
• strict Intent corpus check — zero diagnostics
• graph validation — 246 nodes and 215 edges
• all five semantic-review expected results validated against the enforcement schema
• retired-name CI guard passes for tracked content and paths
• git diff --check

Nix is not installed in the local environment, so the flake lane is left to GitHub CI.